ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
                       ³ Welcome to E! for Windows! ³
                       ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

            *** Please read the following lines before proceeding ***

      Close this window after reading to continue installation.

      A file named READ.ME will be installed in the \EW directory. Please
      read it before running your first editing session.

     ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
     ³Users of E! for Windows 1.xx:³
     ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ

      There are changes in E! 2.0 that you must consider before installing:

      1. In order to support big files, we had to make some changes to the
      API. EWD files compiled for EW 1.xx are not compatible with E! 2.0
      and you should not try to use them. We provide replacement files for
      the sample EWDs. Your own Extension DLLs just have to be recompiled
      using the new include file (EWAPI2.H) or the new import unit
      (EWAPIMP2.PAS). That's all. So, we recommend that you do not
      autoload EWDs until they have been recompiled.

      2. The installation program will automatically translate your
      existing associations to the new layout of EW.INI. However, if you
      are using alternate .INI files you'll have to convert the
      associations manually. Don't worry, it's easy. Associations were
      defined in the [system] section. They are now located in the
      [associations] section.

      In version 1.xx the layout of each association entry was as follows:

      ext=Keyboard Menu CompilerSet ExpansionSet LoadMethod SaveMethod

      The new layout of version 2.0 is as follows:

      ext=Keyboard Menu ExpansionSet LoadMethod SaveMethod HDFName

      Associations between filename extensions and Compiler Command Sets
      are now useless and no longer exist. HDFName is the name of the
      Highlighting Definition File that should be used with files having
      the "ext" extension.

      So, you only have to delete the third token in each existing
      association entry. Use the Associations dialog box to add the
      HDFName if necessary or add it directly if you want.

      3. The installation program will also add default filters.
      ([filters] section) to EW.INI. You can copy this information to your
      alternate .INI files if necessary.

      4. It is no longer necessary to add the \EW and \EW\USER directories
      to your PATH, provided you leave all DLLs and EWX.EXE in the \EW
      directory. The Extension DLLs (.EWD) must reside in your USER
      directory.


      Thanks for your attention.

      MainSoft sarl